Does execute anonymous from Developer Console not enforce heap size limit?

So I logged a case with support (Case Number 14444735) to find out if this limit has actually been lifted, and here's the response I got:

I have verified in Execute Anonymous and the heap limit is lifted extremely. I am currently investigating as why the execute anonymous from Developer Console does not enforce heap size limit. I will provide you with an update as soon as possible.

And some time later:

I have discussed the issue with my seniors and found that heap size checks are performed according to certain heuristics, meaning they are not performed on evaluating each statement, and as a result it is possible to exceed the limit, but this will be enforced as soon as salesforce checks it.

At that point, I asked for more detail and if there is any plan to change this behavior. He came back with:

As of now we have to [sic] information that R&D team is planning to make any changes to this. But currently the heap limit would cause a crash whenever system checks for it.

You can also get more details regarding this from the below mentioned URL: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_gov_limits.htm

I also asked why Limits.getHeapSize() does not count as checking the limit, and he refused to further explain:

I had a discussion with my seniors regarding the evaluation of heap size as how it works internally but the architecture and internal implementation details cannot be shared.

As explained previously we follow certain heuristics to determine when to compute the heap size (which performs a heap walk), and when to enforce the max heap size, which doesn't occur when invoking Limits.getHeapSize().