EDIT: seems like Zeros() is adding to the program size... 3200-(768*2)=~1700 bytes of code.  Sounds a bit more likely, but i thought Zeros() didn't add on to the program size that much

It adds just as much as any other data.  But if you're using a shell, data won't add to the size limit in Axe 1.0.0, but don't rely on that being out before the contest deadline, I'm hoping it will be though.

Awesome menu by the way!

Title screen + intro looks wonderful btw. =)

Made it a working menu, then noticed something.
The whole starting sequence altogether is ~5500 bytes. 

Whoa, that's a lot... I'd suggest finding some way to compress that, but don't cut down on the awesomeness, either

So I'm adding in manipulable objects atm, and I'm wondering what should happen if it finds itself inside a solid [insert tile type here] upon dimension shifting.

See poll.

Added option.  The problem with that would be that the object might be an integral part of the level...unless it drops out of the ceiling afterwards or reappears after a bit or something like that.

EDIT: btw, they're not explosive.  Unless I were to add multiple types
for now it's like the guy is manipulating a brick or something.

EDIT2: I see an "other" vote, could that person specify what they would like? TIA

Go boom. Would be awesomeness.

Time Fcuk freezes boxes until the dimension is reset, which is a great puzzle-maker. If the boxes are disintegrated (I don't mean explosive tearing parts out of the level, but just they explode into nothingness) that could also make for some very cool puzzles.