General timer descrepancies

[Zoster]

In continuation of #1082:

Well I certainly believe that it works for you but the problem seems to be suprisingly wide spread. Please see:

Beware of QueryPerformanceCounter():
​http://www.virtualdub.org/blog/pivot/entry.php?id=106

Performance counter value may unexpectedly leap forward:
​http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q274323&

​http://www.mindcontrol.org/~hplus/pc-timers.html

Not sure what you guys can do about it but I think it should be noted in the help file that those variances might occur. I'm using the @timemacros as a workaround for now.

[Zoster]

PS Before Valik tears me a new one: I'm sorry for opening a new ticket.

[Valik]

Sorry doesn't put all this crap into the old ticket where it belongs.

[J-Paul Mesnage]

Not sure to understand what can be done in this subject.
Do we need to support HW which does not report the high precision counters with correct value?
Do we need to force running the AutoIt process on only one processor to have the high precision counter better in multiprocessor system?

[Valik]

Microsoft lists 9 chipsets that are affected. I really don't think we need to document a problem that's due to a hardware defect on so few chipsets.