Which timers are dependent on system time?

I was trying to solve similar problem. I turn out to use System.Diagnostic.StopWatch to replace all DateTime.Now. StopWatch will use the high frequency clock if present. So, it's more accurate and independent of the system clock change. However, if high frequency clock is not present, it will fall back to use system clock again.

According to my testing, all my machines have high frequency clock, including the machines in VM.

About the Timer, as far as I remember, it isn't dependent on the system clock. However, you don't really want to use Timer to track the time because the Timer callback events may be deferred by some other events.

I'll just quote Jim Mischel comments, as it's the most relevant answer to my question.

None of the timers depend on the system time. That is, the user changing the clock will not affect System.Windows.Forms.Timer, System.Timers.Timer, or System.Threading.Timer. Nor will it affect Stopwatch or Environment.TickCount. Also, there's no "overhead" to using Stopwatch. It's not like the value is continually updated. It's lazily evaluated (i.e. Ticks is updated when it's referenced).

Documentation for Stopwatch says: "TheStopwatch measures elapsed time by counting timer ticks in the underlying timer mechanism. If the installed hardware and operating system support a high-resolution performance counter, then the Stopwatch class uses that counter to measure elapsed time." If you look up info on the high-resolution performance counter, you'll see that it doesn't depend on the system time

Timers are similar. System.Threading.Timer is based on Windows Timer Queue Timers. See that documentation. System.Timers.Timer is just a wrapper around System.Threading.Timer. System.Windows.Forms.Timer is a wrapper around the Windows SetTimer and KillTimer functions. Documentation for those indicates that they are not dependent on the system time.