[Insight-developers] ITK4: OStringStream removal

[Bill Lorensen]

My recent experiment that build Slicer4 against ITK4 illustrates the
impact of API changes.

Back in the day, we recommended that developers use itkOStringStream
rather than std::ostringstream because the latter was not implemented
by all of the itk platforms.

Slicer4 uses itk::OStringStream in these files:
./Applications/CLI/BRAINSTools/BRAINSCommonLib/BRAINSMacro.h
./Applications/CLI/BRAINSTools/BRAINSCommonLib/GenericTransformImage.cxx
./Applications/CLI/BRAINSTools/BRAINSCommonLib/Test_FindCenterOfBrainFilter/ImageCompare.cxx
./Applications/CLI/DiffusionApplications/ResampleDTI/Testing/itkTestMainExtended.h
./Applications/CLI/MRIBiasFieldCorrection/ImageCompare.cxx
./Libs/vtkITK/itkEncodedTransformFileReader.cxx
./Libs/vtkITK/vtkITKArchetypeImageSeriesReader.cxx
./Modules/ChangeTracker/DiffeomorphicDemonsRegistration/ImageCompare.cxx
./Modules/Meshing/IO/itkMimxReadHistogramBinValuesFilter.txx
./Modules/Meshing/Mesh/itkMimxRebinHexahedronMeshTraitDataInPlaceFilter.txx
./Modules/Python/FilteredTractography/weave/scxx/scxx.h