anchor.diff:  * For more details see, https://vanilla-java.github.io/2016/03/24/Microservices-in-the-Chronicle-world-Part-2.html[Using Method Reader/Writers] and https://github.com/OpenHFT/Chronicle-Queue/blob/master/src/test/java/net/openhft/chronicle/queue/MessageReaderWriterTest.java[MessageReaderWriterTest]
   
   ''''
  -* *12. Detailed tracing of timings*
  +===== *Detailed tracing of timings*
   
   Chronicle Queue supports explicit, or implicit, nanosecond resolution timing for messages as they pass end-to-end over across your system.
   We support using nano-time across machines, without the need for specialist hardware.
  
positive.code: ----
  
  '''
  * *9. Reading a queue using `ChronicleReaderMain`*
  
  The second tool for logging the contents of the chronicle queue is the `ChronicleReaderMain` (in the Chronicle Queue project). As mentioned above, it is able to perform several operations beyond printing the file content to the console. For example, it can be used to tail a queue to detect whenever new messages are added (rather like $tail -f).
  
  
negative.code: net.openhft.chronicle.queue.impl.single.SingleChronicleQueue.countExcerpts
  ```
  
  ** *Move to a specific message and read it*
  
  The following example shows how to write 10 messages, then move to the 5th message to read it
  [source,java]
  