Hello,
I would follow Bamdev's suggestion. An alternative is to write a line-search function, similar to the ones you can find in /solvers/linesearch, and to pass it through options.linesearch (as opposed to problem.linesearch).
But even so, those calls actually do not get access to the iteration number k (I suppose we did not see the practical use for it, but that is an oversight). So even that way will not be entirely satisfactory. You could count iterations using storedb.internal of course, which would be a little bit cleaner than Bamdev's hack*, but still.
I'm adding to the TODO list that it would be good for storedb to contain some metadata, such as the proper iteration count. But I do not expect this will be added into a manopt release very soon.
Let us know how you fare,
Best,
Nicolas
* i'm claling it a hack, because everytime you call steepestdescent or conjugategradient on your problem structure, you need to remember to reset to counter to 0, which is not very nice. That would not be the case with the alternative I'm hinting at.