It's a good idea for an inbuilt condition to be able to delay actions - it's something I'll look in to for Construct 2. I don't think it's really possible in Construct 1 - yes, I know I keep saying that - but its event engine architecture really isn't up to it. For now, the Function object's 'Call function after delay' is the standard way of implementing a wait.
I think what zero_rogue is talking about is a wait condition like so:
+ A collides with B
+ Delay actions 3 seconds
-> Destroy B
When A and B collide, 3 seconds later the actions run, and the B that was in the collision is destroyed. (For those in the know, the SOL from the original conditions is preserved when running the actions later on, with destroyed objects removed I guess.) At the moment, using the function object to implement a wait resets all object picking when running the function later on, so in this case, all Bs, including those not involved in any collision, are destroyed. This requires a 'destroy me' flag as a workaround to re-pick the intended B to destroy.
So, this would be a very handy condition. It's on my 'definitely do this in Construct 2' list.