When I look in a database for invalid objects, it cannot detect triggers that reference tables that do not exist.
Since I use triggers to maintain referential integrity, this can bite me if I ever deploy something to Production that contains a reference to a new object that still is undergoing UAT (and yes, we got a middle-of-the-night phone call after our last deploy to fix this).
Part of our release process is to run the Find Invalid Objects check in the database after all deployments, so it would be nice if that could be expanded to detect a problem like the following:
DROP TABLE IF EXISTS dbo.DummyTable
CREATE TABLE dbo.DummyTable (SomeColumn INT NOT NULL)
CREATE TRIGGER TR_ThisWillNotWork
DELETE FROM InvalidObjectThatDoesNotExist WHERE 1 = 1
After creating the table and trigger above on an empty database, Find Invalid Objects returns no results.