Fixed a randomized crash issue with determine-indirect-claim

It seems that object-pattern-match-delay will cause intermittent crashes when
it's contents are only modify-instance calls. The significant part about this is
that modify-instance also delays object pattern matching until finished.
Without perusing the associated clips c code, I can only guess that the issue
has to do with multiple layers of indirection being added. Fixing this issue
required me to remove the object-pattern-match-delay command that surrounded
the modify-instance calls.

I also cleaned up the code to look similar to the wavefront scheduling pass
code in terms of formatting.