It can happen that a VI, or worse a typedef, gets inadvertently pulled into code from another library or class simply to reuse code.
Using "Why is this item in the Dependencies" isn't particularly helpful in a large project.
Could not the offending dependency be marked with hot pink or similar to using a breakpoint? Could the Breakpoint Manager be adapted to finding dependencies?
