Iterating a two-dimensional array will usually be expensive enough to hide the cost of one method call. And it makes it probable that the method does not become nested in any case, even without an attribute, just because there is too much machine code.
But look. Tools + Options, Debugging, General, untick "Disable JIT optimization when loading a module." Select the Release assembly. Set a breakpoint on the method call and run. When it breaks, right-click the source code and select "Go to disassembly". If you see a call instruction, it will not be inserted. You can see some kind of machine code before the call if the method takes arguments.
source share