If you made triggers (and indexes) their own separate root level compare object, it would allow me to identify "time impacting" changes much more quickly. One of the major concerns for us involves having all system deployments occur within a fixed maintenance window at night.
The only real changes that impact that deployment time are column changes to tables with large amounts of data and index creation/altering. It's possible to identify them now, but it could be improved.
While I'm thinking about it, how about a current rowcount for table objects displayed as a column so you can easily identify which tables you need to 'tread lightly' around, similar to the 'Object Explorer Detail' window in SSMS.