You're quite right, this is a bug in SQL Dependency Tracker v2.0 and v2.1.

The fix has been made to our dependency engine itself, and is being tested internally. The next release of Dependency Tracker should fix this issue; I'm afraid I can't give you a date for that at this time.