anchor.diff:  -----------------------
   
   Again we can se that the `expect()` calls follow a record and playback
  -model.  Each one tests a successive call.  This sequence confirms that
  +model. Each one tests a successive call. This sequence confirms that
   we get `"a"`, `"b"` and `"c"` in order.
   
   -----------------------
  
positive.code: section on how to work with doubles>> has a more detailed
  discussion of the algorithm used for comparing floating point numbers.
  
  Then there are two ways to return results:
  
  |===========================================================================================
  |*Macro*                                                      |*Description*
  
negative.code: declared and expected? What happens if a call was made to a mock that
  wasn't expected? And vice versa, if an expected call was not made?
  
  Actually, the thinking is not only a school of thought, you might want
  to switch from one to the other depending on the test. So *Cgreen*
  allows for that too.
  
  By default *Cgreen* mocks are 'strict', which means that a call to
  an non-expected mock will be considered a failure. So will an expected
  