anchor.diff:    ///	  The TestCaseAttribute allows you to specify the name of a function that
     ///	  returns a TValueArray which will be passed into a function that takes
     ///	  parameters. This is really only needed to work around the problens with
  -  ///	  the TestCaseAttribute.
  +  ///	  the TestCaseAttribute.�
     ///	</summary>
     ///	<remarks>
     ///	  Note that the types in the TConstArray should match the parameters of
  
positive.code: 
    ///	<summary>
    ///	  A method marked with this attribute can contain a teardown method that
    ///	  will be run after each all tests in the fixture have executed. Note
    ///	  that if more than one method is decorated with this attribute the first
    ///	  method found will be executed (not recommended!).
    ///	</summary>
  
negative.code: 
      ///	<summary>
      ///	  When true, test fixtures will be found by using RTTI to search for
      ///	  classes decorated as TestFixtures.� Note for this to work you may
      ///	  need to use {$STRONGLINKTYPES ON} otherwise the classes may not get
      ///	  linked as they are not referenced. When False you will need to
      ///	  register the fixtures using TDUnitX.RegisterTestFixture
  