Replace GetTickCount64() with QueryPerformanceCounter().
It turns out GetTickCount64() is only precise to the nearest timeslice, which can be up to 16ms. The imprecision caused test failures.
Showing
Please
register
or
sign in
to comment