stop watch

If accuracy is critical, don't use Windows unless it is the embedded version. If you must use other versions of Windows, then write a device driver to get the best accuracy and don't use a UI. If you can't write a device driver and must use an application with a UI, and a stopwatch implies UI, then you must expect innacuracies.


You can reduce inaccuracies by not using a repeating interval for the timer. Instead, each time the timer event happens, stop the timer and start it again with the amount of time needed for the next tick of your clock.

Dipal the issue with the article you recommended is that is using the window timer, which does not give an accurate interval if you have a busy application. It also depends on the requirements of the stopwatch.

Here is an article from c-sharpcorner. it's somewhat dated (no pun intended!) but you might be able to use the concepts.

http://www.c-sharpcorner.com/UploadFile/aaghany/StopWatchUsingCsharp11122005051620AM/StopWatchUsingCsharp.aspx

I only know of two high resolution timers, the one I use to benchmark code is the Stopwatch under the System.Diagnostics library.
System.Diagnostics.Stopwatch

The other is the the timer under the DirectX framework or their utility class.