VBOX corrected time
It seems as there are many ways of measuring VBOX times. This is what I learned.
The different methods show a big difference in time results, I present the results from the same 100-200 run.
Visual time 7.4s
Visual check of what the display is showing.
Good but not accurate as it doesn't take altitude changes into account
See first Image attached below
Verified time 7.37s
Extract the .DBN file from your VBOX and upload it to:
http://vboxverify.com/
This will only accept times with ~2% altitude difference, if larger delta they will be classed invalid
See second Image attached below
Corrected time 7.28s
This is where it get's interesting, if your driving down a large slope your times will always be magic. This method takes the altitude differences of the run into account and corrects it accordingly.
As you can see in the blue graph my run was performed on an increasing altitude.
See second Image attached below
By using the DB Scanner tool the altitude changes are taken into account. In my case that was positive for the end results
See third Image attached bellow
Sure, these margins are smal but in a hobby where 5 hp makes a difference this is as applicable

. Yes, it doesn't take wind into account
First Image
Second Image
Third Image
