TimeTicks currently has a workaround for past QueryPerformanceCounter challenges. Past issues include correctness, precision and cost of reading. These are supposed to fixed in newer versions of Windows. This bug tracks always using QueryPerformanceCounter.

Need to verify the performance cost of QueryPerformanceCounter, on Win7, with a variant time stamp counter CPU, before enabling.

See also:
https://docs.microsoft.com/en-us/windows/desktop/SysInfo/acquiring-high-resolution-time-stamps#qpc-support-in-windows-versions
https://chromium-review.googlesource.com/c/chromium/src/+/1413055