nsiTimer platform differences

[Tony C]

We're seeing a timing issue when using nsITimer on MSWindows that does
not occur on GNU/Linux.

A javascript XPCOM component sets a TYPE_ONE_SHOT timer to go off in
one hour. The timer does not go off until significantly (more than 2X)
after that, and the delay seems to be related to what hapens in the
chrome code, apparently having to do with other timers being used
there, though the timer-interaction part is a bit of a guess on my
part.

Anyone else seems different nsITimer behavior on Windows or have any
sort of explanation about whether this is a problem with the win32
timer implementation, or whether there is some workaround?

Thanks.