Fix timing accuracy about strikebox HOT 1 OPEN

Historically, there's been done more research on the topic; Here a few similar reports from around the world:

http://www.geisswerks.com/ryan/FAQS/timing.html
http://www.virtualdub.org/blog/pivot/entry.php?id=272
https://omeg.pl/blog/2011/11/on-winapi-timers-and-their-resolution/

What it boils down to, is that timeSetPeriod(1)+timeSetEvent() and busy-wait loops (using QPF+QPC) are most reliable, combining them together makes for the most accurate and precise timing

Also related :
https://en.wikipedia.org/wiki/Accuracy_and_precision#ISO_definition_(ISO_5725)
https://stackoverflow.com/a/29183085/12170
https://stackoverflow.com/questions/7685762/windows-7-timing-functions-how-to-use-getsystemtimeadjustment-correctly
http://blog.nuclex-games.com/2012/04/perfectly-accurate-game-timing/
https://redream.io/posts/improving-audio-video-synchronization-multi-sync
https://www.gamasutra.com/view/feature/171774/getting_high_precision_timing_on_.php?print=1

EDIT Oh, and :
https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/timer-accuracy

from strikebox.