I agree on all counts. I might have been suspicious of the cause had I not been able to inspect it as a janitor. In fact, I had already done that before reading this thread, because I was confused about how I should be evaluating the code.

OP chose strange formatting. It makes it hard for people to see the code as one contiguous element. A Janitor could fix it, but would have to make decisions that are best made by the OP. If the OP doesn't resolve them, someone could send him or her a friendly message mentioning the issue.

If it were anonymously posted I'd jump right in and fix it because AM can't fix his own posts. Since it was posted from a real account, I prefer to let the OP do the right thing, and step in for the really bad issues.

The title isn't great either. It's not an Inline-based leak. It's a user-created leak based on his manipulation of perlguts/perlcall/perlapi. Inline just processed the code.