Does anyone know of a way to suspend triggers - without dropping them - from running when executing an insert from T-SQL?

I've got a table that when inserted into fires off a trigger which populates another table. Under normal circumstances I'd be OK with that, but it's messing up later insert statements into that other table, and I need to be able to control the IDs (they are GUIDs so IDENTITY INSERT OFF/ON isn't an option). I need to be able to insert into this table, then the child/related table.

I hate triggers...

-tg