BUG: VTKImageIO did not respect endianness for streamed writing/reading

VTKImageIO did not change endianness from native to big-endian when writing
/ big-endian to native when reading files. This resulted in different results
when using a streaming and not streaming pipeline. Changed behavior to
non-streaming behavior.
A test for comparing block reading/writing to streamed reading/writing is
added.

Included proposals form Matt McCormick:
 - moved convenience methods from ImageIOBase to private methods in
   VTKImageIO
 - using quotes instead of brackets for includes of ITK headers
 - using FillBuffer instead of ImageRegionIterator
 - keep own compare function to be able to compare only the buffered region

Change-Id: I184e78b35bab155db47be3733197b39235d9bcf1
COMP: Conditionalize insane "#define inline" in libtiff

This was causing mysterious linker errors if building
against the OS X 10.9 SDK.  Limit it to MS compiler,
which does not support 'inline' in C.

Suggested-by: Sean McBride <sean@rogue-research.com>

http://review.source.kitware.com/#/c/12924/3

Change-Id: Ic72f744d0b9b68412d65792ca1430a9151d7080a
BUG: Make ImageIOBase::SetDirection accept const reference parameter

Change-Id: I7bf950866d8cb1328ebc02f8fc5579c98f801664
Merge topic 'streamingbug'

aab40f1 BUG: VTKImageIO did not respect endianness for streamed writing/reading
Merge topic 'tiff-inline'

08bf6be COMP: Conditionalize insane "#define inline" in libtiff
Merge topic 'ImageIO-const'

fe6c419 BUG: Make ImageIOBase::SetDirection accept const reference parameter