Delayed Collision Detection on Instantly Overlapping Objects. Why?

Is there a science to when collision detection is... detected?

Say you have an object that, when reaching a certain animation or end of animation, it creates a second invisible detector object that flashes instantly and then destroys itself maybe a frame or two after. When objects that are considered enemies touch this detector, they'll be destroyed. Making this work is not a problem.

But sometimes, the timing is off. Objects that are enemies being touched at the detector object's creation are destroyed... but often times not in that instant they're colliding or overlapping. It's a frame off, or sometimes even two or three. Is this a known problem with a lot of lines of code or large separations in code? Not sure how to fix or workaround this so that it occurs at the very instant the detector object is create (which would have it already overlapping an enemy object)

After a bit of tweaking, I got it down to a one frame delay. I went and looked over things again and realized that some code was out of order because of the way ForEach loops work, which has now given me an answer to something else I suspected! (Whether or not ForEach loops and fast loops trigger before everything else).

What I'm not sure of now is if it's possible for there to be zero frames in between collision detection. Example, Object A creates Object B on top of Object C, which destroys Object C, all in one frame sequence.

Or would it be the fact that there are a lot of alterable values and directional changes and the like being associated with those lines that are making the processing issue complicated?

On second thought, I didn't figure things out but found out, or recreated, the problem. I specifically put in things similar to how I have my code in a larger project, checking for Health alterable values and subtracting it, and upon having none, setting the object up to be destroyed.

This works fine in normal circumstances, but not if the object is being automatically created, possibly during events that don't call for immediate activation ("user clicks with left mouse button" versus "when object is playing x frame.")

In the frame labeled Clicking, you'll see the Enemy object being destroyed the instant the Detector appears.
In the frame labeled Self Spawning, however, you'll see the Enemy object linger around for an additional frame when overlapping the Detector before it is destroyed.

No idea why this happens.

Please login to see this attachment.

The example you posted, with ForEach loops, seems to work... intermittently. Again, not sure why, but "most" of the time, it destroys the instant there is overlap. And then there's a small percentage chance that it's a frame later.

Switching it to Overlapping seems to work every time though! The only problem I have with that is that if I use Overlapping, it will then trigger multiple times; it will trigger at every frame. And I would like it to only happen once while also avoiding "only one action when event loops" as that tends to lock functionality if I needed to check for multiple instances.

Victory! It worked! And, yes, that definitely isn't my real project. I'm not going to make a "Aqua Diamond Destroyer" game. :p

Thanks for your help!