Hi PaQ, it's a bug in the surface/surface intersection calculation.

This particular one does not look like an easy one to tune up myself, but I have bundled it up and sent it to IntegrityWare so that they can take a look at fixing it in the library.

- Michael