NAT is orthagonal functionality to the VPN server functionality.
The expected network topology of the "Remote access (dial-up or VPN)" configuration choice in the Wizard is a server with a NIC connected to the public Internet and a NIC connected to the LAN. The Internet NIC will listen for incoming connections and, once a client has connected and been assigned an IP address (either by DHCP relayed from the LAN or via a static IP address pool on the RRAS server) packets from the PC will be decapsulated and dropped on to the LAN interface (which will also perform proxy ARP for VPN clients automatically). In this configuration, no NAT is configured. The VPN clients don't need NAT anyway, since they're being assigned LAN IP addresses when they connect. (You can see any example of the expected topology in the help topic "Common Remote Access Configurations" under "Overview of Routing and Remote Access" in the product's help.)
If you want NAT, too, you'd choose "Virtual private network (VPN) access and NAT". This is a common configuration where a single server is being used as both a NAT router for the LAN and a VPN server. It's a very similiar configuration to the "Remote access" configuration, but you'll also be configuring the Internet NIC to be, effectively, the "outside" interface for the NAT functionality.
As a point of note: You can configure a RRAS VPN server with a single NIC. You have to use the "Custom" configuration choice in the wizard to do so, but it'll work fine. You'll need to forward the appropriate protocols through the edge firewall to the VPN server. It will receive incoming client connections on the same NIC that it decapsulates packets onto and performs proxy ARP with.