Improving LeetCode timing of Rust Solutions

I have recently signed up to LeetCode to use the problems to improve my Rust skills. One frustration on the solutions I have submitted so far is that when a solution is accepted, it seems as if LeetCode is expecting runtimes of many milliseconds, where many in fact run in less than a millisecond. This means that most submissions from multiple users get a "fastest of 100%" rating, with "0 ms" runtime!. Is there a possibility of LeetCode increasing the granularity of the timing measurements - I'm guessing this may affect other fast compiled languages such as C as well?

Comments (2)