#0 in SystemVerilog inactive event region

I guess #0 comes in handy when we try to model a sequence of events within one timeslot, and we want to guarantee those events in deterministic order, assuming no dependency on/from other process of another set of events.

In reply to dave_59: