When more than one Windows Event Log is created within the same second, the sort/display order can be different than the order in which they were written. The index seems to be the reverse order in which they were written: LIFO, not FIFO.
I wrote code to read event log entries and both the TimeGenerated and TimeWritten are rounded to the nearest second. They do not have millisecond-resolution.
So, is there any way to get better resolution on Windows Event Log objects, for writing or reading? Maybe with a registry switch or code?
One solution to this would be to not use the Windows Event Log for data like this, and having higher-level events point to file logs with more detail. Another code solution would be to use the binary data field to store a timestamp in ticks. Then I can use a custom program to read/sort the log and use that data for finer resolution when it's available. But I'd prefer to avoid that hack which only applies to custom entries anyway.
I'm guessing a question will come up about "why do you care" or "that's not how the log should be used". Let's skip forward from that to specific technical answers. Thanks.