anchor.diff:  NOTE: BlockingBucket and ScheduledBucket do not provide the verbose analogs. VerboseResult has no sense for this kind of buckets because interactions with them can be followed by thread sleep or delayed execution, so VerboseResult can be absolutely stale and irrelevant to the moment of time when control over execution is being returned to your code.
   
   ==== Principles of result decoration
  - * void return type always decorated by `VerboseResult<Void>`
  - * A primitive result type like long, boolean always decorated by correspondent boxed type for example `VerboseResult<Boolean>`
  - * None primitive reult type always decorated as is, for example `VerboseResult<EstimationProbe>`
  +* void return type always decorated by `VerboseResult<Void>`
  +* A primitive result type like long, boolean always decorated by correspondent boxed type for example `VerboseResult<Boolean>`
  +* Non primitive reult type always decorated as is, for example `VerboseResult<EstimationProbe>`
   
   ==== Example of Verbose API usage
   [source, java]
  
positive.code:     httpResponse.setContentType("text/plain");
      httpResponse.getWriter().append("Too many requests");
  }
  ----
negative.code: [[verbose-api]]
  === Verbose API
  Verbose API:: is the API whose intent is in injecting low-level diagnostic information into results of any interaction with a bucket. Verbose API provides the same functionality as Regular API, with one exception - result of any method always decorated by `VerboseResult` wrapper.
  
  VerboseResult:: is the wrapper for interaction result that provides the snapshot of bucket and its configuration that was actual at the moment of interaction with bucket.
  
  