MPLS Static Routes vs Dynamic

When using MPLS VPN to a service provider I'm not a huge fan of service provider managed static routing.  I would prefer to inject whatever routes I want to the MPLS cloud.  For this of course you will need to have a CE router advertise BGP to the service provider.  A fully dynamic model would assume you redistribute your entire IGP routing table into BGP and therefore MPLS.   Below is an example of providing individual host routing across the MPLS VPN.  Only the static routes tagged with 100 are advertised into BGP

route-map tp-host-routes permit 10

 match tag 100

 set origin igp

router bgp 65111

 no synchronization

 bgp log-neighbor-changes

 redistribute static route-map tp-host-routes

 neighbor 192.168.1.1 remote-as 65002

 no auto-summary

int fa 0/1

 ip address 192.168.1.2 255.255.255.252

 no shut

 description SP

 speed 10

 full-duplex

ip route 172.16.1.5 255.255.255.255 lo 1 tag 100