Martin,
IKEv2 is standards based and will always be easy to get accreditation (if you work with financial or government partners).
SSL is mostly using proprietary solutions (i,e, there is hardly-or-no interoperability between vendors), but it will allow you to do more cool things - like update the client.
A nice compromise is ASA + Anyconnect IKEv2. Where You can use IKEv2 to exchange data, but still retain some of the benefits of SSL (client/profile updates for example).
It all depends on what you're looking for.
M.
edit: I tried to keep it brief, this is a topic you can probably write a lengthy article on.