Reading some binary STL Files will fail

[imikejackson]

The binary STL specification allows STL files to store up to unit16 bytes worth of information at the end of each triangle. The current code simply ignores that value. While the vast majority of files set that value to zero or incorrectly set it to a non-zero and but don't write anything further to the stream, there are more and more manufacturers that use STL files in the additive manufacturing world (Magics Materialise being one) that do in fact use those 65K bytes to write information about each triangle. The code should take into account how much to move the input stream forward after each triangle.