anchor.diff:  
   Chronicle Wire allows (and encourages) objects to be re-used in order to reduce allocation rates.
   
  -When a marshallable object is re-used or initialised by the framework, it is first reset by way of `Wires.reset()`.
  +When a marshallable object is re-used or initialised by the framework, it is first reset by way of `Marshallable.reset()`
  +which is recommend over calling `Wires.reset()`.
   In the case of most DTOs with simple scalar values, this will not cause any issues.
   However, more complicated objects with object instance fields may experience undesired behaviour.
   
  
positive.code: [source,Java]
  ----
  // the same code as for text wire
  wire2.write(() -> "message").text("Hello World")
          .write(() -> "number").int64(1234567890L)
          .write(() -> "code").asEnum(TimeUnit.SECONDS)
          .write(() -> "price").float64(10.50);
          System.out.println(bytes2.toHexString());
  ----
  
  
negative.code: 
  [source,Java]
  ----
  wire.write("message").text("Hello World")
        .write("number").int64(1234567890L)
         .write("code").asEnum(TimeUnit.SECONDS)
        .write("price").float64(10.50);
  System.out.println(bytes);
  ----
  
  