If you replicate what I have done, you will be able to write Artemis software in C or C++ with full access to the Ambiq Suite libraries. The best feature is that attaching a J-Link EDU or J-Link Mini will allow you to reflash firmware, examine call stacks, set breakpoints, watch variables, and do everything that a hardware debugger enables you to do, all of it integrated natively into the SES IDE.
I have found it hugely useful to use the SES symbolic directories to include the Ambiq Suite sources in every project. Doing so enables you to use the SES editor to walk through the Ambiq sources, or jump directly to where one of your Ambiq HAL calls is defined so you can see how it works. You can even single step through the libraries or set breakpoints inside them just like any other software you write. And of course, when the program you are writing crashes into the ARM hardfault handler for the umpteenth time, the hardware debugger lets you work backwards through the callstack to find out why.
There is also support for the Segger IO debug mechanisms so that you can use printf() to send data to a terminal window hosted by the debugger. The IO goes over the debug connection meaning that the processor's entire hardware resources are still available to your application.
I am happy with how it all turned out. However, I will say that it was not the most intuitive process for me to get everything working, and it is quite likely that some things I did were non-optimal due to me having to learn SES as I went. If you want to give it a try yourself, I have attached a document that describes how you can replicate my setup. This process has been tested by a couple of volunteers, so it should be mainly debugged at this point. Feel free to send me a reply or a PM if you have a better way of doing this stuff and I will do my best to keep the doc updated. I am hoping that the document will come through as an attachment. It is a zipped PDF.