You can turn off NAT altogether with v7.0 for the Pix or ASA.
But assuming you don't want to turn off NAT or you can't because your are running an earlier version of code, if you want traffic to be initiated from the DMZ to the inside you will need the static statement.
If traffic was only ever initiated from inside to the DMZ you would be fine with your "nat (inside) 0 access-list NoNatinside" statement.
NAT 0 with an ACL is bi-directional. Meaning hosts on lower security level interface (like your DMZ) will be able to initiate connections to host on higher security level interfaces (like your inside). (Assuming the ACL on the dmz interface permit the connections.)
NAT 0 with a network (ie: nat (inside) 0 10.10.10.0 255.255.255.0) works as Jon described. Hosts on the dmz would not be able to initiate the connection.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...