To be honest I have never had to resort to ever trying such a NAT configuration on the software level you are using.
Though to my understanding its possible in the newer software 8.3 and newer with the new NAT configuration format
There the configuration could look something like this
object network STATIC-PAT-1
nat (LAN,WAN) static interface service tcp www www
object network STATIC-PAT-2
nat (LAN,WAN) static 220.127.116.11 service tcp www www
Both NAT rules seemed to work fine with regards to testing them with "packet-tracer" command.
Seems the behaviour is a bit different on different devices.
I for example tested the configuration format you used in a Cisco FWSM which accepted and entered both "static" commands even though giving the warning. An ASA 5510 running 8.2(2) on the other hand gave the warning and rejected the second command.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...