Hi guys,
There was a bug in the displacement triangle intersection code causing this issue that I just fixed.
The issue gets more obvious the more samples are rendered, so you may want to lower the number of samples of your info passes to circumvent it until a new version is released with the fix.
Thank you for the report and apologies for the inconvenience.