ID 394039 - DeepHoldout produces incorrect results when the Deep pixels intersect

Problem summary
DeepHoldout produces incorrect results when the Deep pixels intersect

This applies to both the DeepMerge(holdout) and DeepHoldout nodes

Customer reported version
nuke.11.3v4

Customer reported platform
windows10

Steps to reproduce

1) Open the attached Nuke script

2) Notice the roto shape isn't shown in the Deep image

Below shows the incorrect Nuke 11.3v4 result on the left and the correct Nuke 11.3v3 result on the right

Expected behaviour
For Deep pixels the intersect to be held out correctly

Actual behaviour
If one Deep pixel is completely inside another, then the DeepHoldout operation does not work correctly

Reproduced by support

This problem has been reproduced on:

Nuke 11.3v4 - Windows 10 - CentOS 6.9 - MacOSX 10.13 - regression

Nuke 11.2v6 - Windows 10 - CentOS 6.9 - MacOSX 10.13 - regression

Unable to reproduce in:

Nuke 11.3v3 - Windows 10 - CentOS 6.9 - MacOSX 10.13

Nuke 11.2v5 - Windows 10 - CentOS 6.9 - MacOSX 10.13

Earliest version tested
Nuke 11.2v5 - This issue no longer appears in this version and has regressed