I don't know why, but it appears that the offset with negative setting are causing issues with the geoemtry. Your offset is of a very small value, so I guess this is why you're not having any issues.
For me, the 16 bit version was a little better than 32 bit file. I was working with a displacement which needed a larger negative value, which still caused geometry issues.
The issue seems like the shift uses a different calculation to the displacement. So if you have a large negative value it invariably tears bits of geometry.
Windows 8 Pro | i7 3770 OC | 32 GB Ram | Single Titan (plus Black Edition on Order) | Octane Lightwave |
This is fixed using a ClampTexture node between the texture and the displacement node. The explanation of this is: Octane assumes gets the 32 bit value of an image, therefore there might be higher than 1 and lower than 0 values. The Clamp node corrects the interpretation issues.