High-resolution CPU usage information for batches and statements
Durations made visible by SQL Server vary in their resolution and accuracy.  

SqlWorldWide has an excellent answer showing some of the details.

Be aware of over-profiling SQL Server.  Just like in quantum physics trying to measure the duration of a query too accurately will decrease the performance of the query itself.  In other words, the very act of measuring undermines that which you are attempting to measure.  Measure the performance of a group of queries instead of trying to measure the performance of each individual statement.  If you need to understand why a single particular statement is running slowly, isolate that statement and evaluate it while letting the rest of the group run normally.  Being aware of how SQL Server operates can be tricky enough, let alone trying to see if a query duration was 6 or 600 microseconds.