Feature Request: Improved Timer Accuracy and Reporting for Fossil Test

[dreamer-coding]

Is your feature request related to a problem? Please describe.
The current timer functionality in Fossil Test lacks precision and detailed reporting. This makes it difficult to measure the performance of functions or tests accurately, especially for time-critical or high-performance code. I’m frustrated when timing information is inconsistent or doesn’t provide enough granularity to analyze performance bottlenecks.

Describe the solution you’d like
I would like Fossil Test to include enhanced timers that provide:
• Higher accuracy using system-specific high-resolution timers (e.g., clock_gettime on POSIX or QueryPerformanceCounter on Windows).
• Support for measuring execution time in nanoseconds for detailed performance analysis.
• Detailed reports, including average, minimum, maximum, and standard deviation of execution times across test iterations.
• Annotations to track timing for specific code blocks, not just entire test cases.
• Optional logging of timing data to an external file for performance trend analysis over time.

Describe alternatives you’ve considered
• Writing custom timing utilities for each test, but this is repetitive and prone to inaccuracies.
• Using external profiling tools, which can be overkill for small tests and difficult to integrate into Fossil Test workflows.

Additional context
Accurate timers are essential for performance testing and optimization. This feature could also include built-in support for benchmarking tests and flagging those that exceed defined time thresholds, improving overall code efficiency.