Cisco Firewall :: ASA 5550 / RFC 1918 - Tunnel Terminates At Outside Interface

I've recently set up a LAN-2-LAN VPN tunnel to a 3rd party service provider who uses RFC 1918 private addressing internally and cannot perform NAT on their side of the tunnel.  In order to avoid conflicts with our address space I've had to implement DNAT for the address on the 3rd party network that users at my end must access.  The tunnel terminates at my end on the outside interface of an ASA-5550 running 8.4.2.  While the ASA has 8 interfaces at security levels between 0 and 100, DNAT only need occur for traffic flowing from inside (100) to outside (0).

The following (redacted) addressing applies:

Address of the server on the 3rd party provider network: 192.168.2.155

Mapped address of server as seen on the network at my end: 10.168.2.155

I've currently implemented DNAT using object NAT as follows:

object network remote-server
host 192.168.2.155
nat (outside,inside) static 10.168.2.155

This works as expected, however in examples and discussion I've seen, it appears that the typical way to configure NAT for this scenario is with manual NAT as follows:

object network remote-server
host 192.168.2.155

object network remote-server-mapped
host 10.168.2.155

nat (inside,outside) source static any any destination static remote-server-mapped remote-server
 
Is there any reason why I should consider using the manual NAT method rather than the object NAT method in this scenario?Are there any technical reasons why using object NAT in this manner should be avoided?