The CriticalSectionMetricsReportWaiters unit test is flaky because, after one of the test threads starts sleeping for 20ms, the other thread has to get scheduled within a 10ms window to start capturing the statistics. Otherwise the assertion that the thread waited for at least 10ms fails.

The test should be fixed to not assume the OS will schedule the threads in a particular way.