Refs #7429. After further review, permanently removing bounds checks.

Due to the restriction of weak ordering on the sorted boxes and that all the
boxes save the same signal strength, the sorting order of the boxes is
arbitrary. Therefore, the associated events (one per box) can be at any
location, so bounds checking the final VTK dataset is impossible.

Code/Mantid/Vates/VatesAPI/test/vtkSplatterPlotFactoryTest.h

@@ -106,16 +106,6 @@ class vtkSplatterPlotFactoryTest : public CxxTest::TestSuite
     TSM_ASSERT_EQUALS("No signal Array", "signal", std::string(product->GetCellData()->GetArray(0)->GetName()));
     TSM_ASSERT_EQUALS("Wrong sized signal Array", expected_n_signals, product->GetCellData()->GetArray(0)->GetSize());
 
-    /*
-    //Check dataset bounds
-    double* bounds = product->GetBounds();
-    TS_ASSERT_EQUALS(-8.0, bounds[0]);
-    TS_ASSERT_EQUALS(8.0, bounds[1]);
-    TS_ASSERT_EQUALS(-8.0, bounds[2]);
-    TS_ASSERT_EQUALS(4.0, bounds[3]);
-    TS_ASSERT_EQUALS(4.0, bounds[4]);
-    TS_ASSERT_EQUALS(4.0, bounds[5]);
-    */
     product->Delete();
   }