anchor.diff:  
   In addition to the metadata fields, `@Counted` has the following field:
   
  -`monotonic`:: If `false` (default), the counter is decremented when the annotated method returns, counting current invocations of the annotated method.
  +`monotonic`:: If `false` (default), the counter is incremented before the annotated method is invoked and
  +decremented after the annotated method returns, counting current invocations of the annotated method.
  ++
   If `true`, the counter increases monotonically, counting total invocations of the annotated method.
  -
  -WARNING: The normal expectation is that each invocation of of a method marked with `@Counted` would result in the
  ++
  +WARNING: The intuitive expectation is that each invocation of a method marked with `@Counted` would result in the
   respective counter being increased by one. This is not the case with the default semantics of the `monotonic` flag.
    +
   If you want the counter being increased on each invocation you need to use `@Counted(monotonic = true)`.
  
positive.code: 
  ===== METHOD
  
  When a method is annotated, the implementation must register a counter for the method using the <<annotated-naming-convention>>. The counter is incremented and/or decremented according to the `monotonic` field when the method is invoked.
  
  .Example of an annotated method
  [source, java]
  
negative.code: 
  ===== CONSTRUCTOR
  
  When a constructor is annotated, the implementation must register a counter for the constructor using the <<annotated-naming-convention>>.
  The counter is treated according to the `monotonic` field when the constructor is invoked.
  
  .Example of an annotated constructor
  [source, java]
  