title: Is Stopwatch really broken?
body: <p>At MSDN page for <a href="http://msdn.microsoft.com/en-us/library/system.diagnostics.stopwatch.aspx" rel="nofollow noreferrer">Stopwatch class</a> I discovered link to <a href="http://kristofverbiest.blogspot.com/2008/10/beware-of-stopwatch.html" rel="nofollow noreferrer">interesting article</a> which makes following statement about Stopwatch:</p>
  
  <blockquote>
    <p>However there are some serious issues:</p>
    
    <ul>
    <li><p>This can be unreliable on a PC with multiple processors. Due to a bug in<br>
    the BIOS, Start() and Stop() must be executed on the same processor to get 
    a correct result.</p></li>
    <li><p>This is unreliable on processors that do not have a constant clock
    speed    (most processors can reduce the clock speed to conserve
    energy). This is explained in detail <a href="http://www.virtualdub.org/blog/pivot/entry.php?id=106" rel="nofollow noreferrer">here</a>.</p></li>
    </ul>
  </blockquote>
  
  <p>I am little confused. I've seen <a href="https://stackoverflow.com/questions/232848/wrapping-stopwatch-timing-with-a-delegate-or-lambda">tons of examples</a> of using Stopwatch and nobody mention this drawbacks. How serious is this? Should I avoid using Stopwatch?</p>