Comment by phire

That's high precision clocks (aka Preformance.now(), with sub-millisecond resolution) not timers.

The precision of setTimeout has never been high, it kind-of maps to the OS scheduler and the OS scheduler often enforce their own minimum timeouts (Windows has defaulted to 15.625 ms resolution for a very long time, and the newer high resolution timers max out at 1ms across most operating systems)